Method for Automatic Information Capturing of Communication Events

ABSTRACT

This invention provides a method for automatically integrating and assembling the timestamp of a communication event with the identification of the communicating parties and available event attributes, presenting prompts for user entries on a terminal or interface device, storing user annotated information related to said communication event, and transmitting saved information of said communication events to another terminal device or information system. The invention also relates to a computer program, a device, and a system encapsulating computer programs realizing the method.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.11/465,015 filed Aug. 16, 2006, and claims the benefit of U.S.Provisional Application No. 60/595,940, filed Aug. 19, 2005, entitled“Method for Automatic Information Capturing of Communication Events,”which applications are incorporated herein in their entirety byreference as if fully set forth herein.

FIELD OF THE INVENTION

This invention relates to a method for automatic information capturingof communication events and executing user policy associated with theevent on a terminal or interface device and transmitted to relatedinformation system. This invention relates to a computer program anddevice implementing the method. Additionally, this invention relates toa system encapsulating computer programs implementing the method.

BACKGROUND OF THE INVENTION

Mobile devices have separate lists of call and message events. It iscumbersome for users to transfer such information to journal even on thesame mobile device. As mobile devices play more crucial role in personaland professional communication, mobile users need automatic logger tocapture, organize, and transfer such events with editable attributes orinformation to calendar, agenda, or bulletin on mobile device for recordkeeping and improves work efficiency.

Although each voice call or mobile message is logged by the mobiledevice, the information is kept separately in different categoriesoutside of user's calendar. Currently, mobile device user needs to lookfor a category, record specific date, time, abstract of thecorrespondence, and to manually transfer all related information of acall or message to a specific program. Such manual process iserror-prone and time-consuming for a user who needs efficientinformation capture from a mobile device.

With fast development of network speed and versatile devicefunctionality, conventional communication events such as call,messaging, broadcasting, documentation transmittal, etc., can berealized on any terminal device with network connectivity and relevantcommunication applications. On certain communication systems containingseveral types of terminal devices, vital information related to acommunication event is assembled from different sources in a fragmentedprocess similar to the scenario in mobile devices indicated above. Asmore information and entities are involved in a communication event,automatic integration of communication events with correspondinginformation achieves reliability and efficiency.

SUMMARY OF THE INVENTION

Accordingly, an object of the present invention is to provide a method,in which caller identification (CallerID) or Return Address of thecommunicating parties are automatically captured and integrated withtimestamp of the communication event to an entry page on a terminaldevice prompting for user preference and annotation. An embodiment ofthe invention is for a custom-built application working with nativecommunication procedural interface components of the terminal device andwith contact data to obtain caller identification in a humanunderstandable format, e.g., caller's name, or phone number, or emailaddress, etc.

In order to accomplish the above object, an embodiment of the presentinvention is automatically combining the human understandable calleridentity with a timestamp local to the terminal device. Integratedinformation is presented to the mobile user with prompts in textual,voice, or multimedia format requesting for optional annotation to thiscommunication event.

A preferred embodiment of the invention is automatically includingavailable attributes of the communication event in human recognizableformats in conjunction with rendering prompts for user's annotation tothe communication event. In an embodiment, event attributes such asvoice or message type can be captured from native components on theterminal device in textual, vocal, and multimedia formats.

In accordance with another embodiment of the present invention, theautomatically generated user prompts are in various forms such ascommands, open questions, menus, options, etc. to best represent thecharacteristics of the custom-built application. An embodiment of theinvention automates communication event generation for mobile deviceusers to save to custom applications such as calendar, agenda, bulletin,etc. for further data or information processing.

Another object of the present invention is to provide a method forautomatically integrating and storing user annotations to thecommunication event with event timestamp, contact identifications, andrelated event attributes.

In order to accomplish the above object, an embodiment of the inventionautomates the incorporating of user annotation such as key words,labels, memos, etc. captured by the user prompts, with the communicationevent in a custom-built application. Various formats of user annotationscan be utilized for best efficiency in a custom-built application. Thesecond embodiment of the invention can be a voice-based applicationwhich integrates a communication event with audio annotation from user,and saves the annotated event to the terminal device. Stored eventinformation can be retrieved automatically to a speech projectmanagement system without further manipulation from the user.

Another object of the invention is to provide a method for automaticallyretrieving and transmitting of the stored, augmented information of thecommunication event to current or secondary devices and systems throughvarious network connections.

In an embodiment of the invention, saved communication events can beviewed, edited, and transferred from the terminal device by a dataprocessing application, a component or means performing tasks such assearching and archiving, to a remote server via a network connection.

There is a computer program implementing the invention comprisesintegrating and assembling the timestamp of a communication event withthe identification of the communicating parties and available eventattributes, presenting prompts for user entries on a terminal orinterface device, storing user annotated information related to saidcommunication event, and transmitting saved information of saidcommunication events to another terminal device or information systemfor data processing purpose.

In accordance with another embodiment of the present invention, there isa provided software product that comprises a method for integrating andassembling the timestamp of a communication event with theidentification of the communicating parties and available eventattributes, presenting prompts for user entries or automaticnotification of said communication event, storing information related tosaid communication event on interface devices and/or informationservers, transmitting saved information of said communication events toanother terminal device or information system for data processingpurpose.

The device implementing the invention comprises means for integratingand assembling the timestamp of a communication event with theidentification of the communicating parties and available eventattributes, for presenting prompts for user entries or automaticnotification of said event, for storing information related to saidcommunication event, for transmitting stored data of said communicationevents to another terminal device or information system for dataprocessing purpose.

The system encapsulating computer programs implementing the inventioncomprises integrating and assembling the timestamp of a communicationevent with the identification of the communicating parties and availableevent attributes, presenting prompts for user entries or automaticnotification of said event, storing information related to said event onpersistent storage, transmitting stored information of saidcommunication events to another terminal device or information systemfor data processing purpose.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and other objects, features and advantages of the presentinvention will be more apparent from the following detailed descriptionwith reference to the appended principle drawings, in which:

FIG. 1 is a sample functional block diagram of the inventionillustrating the automatic information annotation to a communicationevent dictated by the user and application policy settings;

FIG. 2 is a data flow diagram showing the event-driven informationassembly and preparation for user's annotation;

FIG. 3 shows an example of the invention of which an extraction modulecollects information of a communication event from a commonly availabletelephony module.

FIG. 4 is a data flow diagram showing user settings and extracted callerID are processed according to local data available to the terminaldevice;

FIG. 5 is a flow diagram showing user can customize how the informationannotation is saved with provided policy templates and program libraryon the terminal device;

FIG. 6 is a flow diagram showing how the pre-determined user policy isused for saving and linking the annotated communication event intovarious application data formats;

FIG. 7 illustrated an interactive method for user to determine theapplication data saving and linking policy at the end of thecommunication event;

FIG. 8 shows an example of the invention of which cross link ofannotated data is carried out for two application modules;

FIG. 9 is a flow diagram showing assembled user annotation andcommunication event data are saved into various formats for differentapplications;

FIG. 10 illustrated an example of retrieving and depositing savedcommunication event with annotation;

FIG. 11 shows an example of the user settings on the terminal device;

FIG. 12 shows an example of the user policy selection on the terminaldevice;

FIG. 13 illustrates the saved application entries related to thecommunication event according to the user policy in FIG. 12;

FIG. 14A and FIG. 14B illustrate different call logger pages generatedby the user policy from FIG. 7 and FIG. 6;

FIG. 15A and FIG. 15B show user annotates the communication event ondifferent call logger pages generated by the user policy from FIG. 7 andFIG. 6;

FIG. 16A and FIG. 16B illustrate the saved communication event from FIG.15A and FIG. 15B separately;

FIG. 17 is an example showing how user can verify the savedcommunication event and contact name annotation using a searchapplication on the terminal device;

FIG. 18A and FIG. 18B illustrate linked events to a contact isaccessible from the contact directory application;

FIG. 19A and FIG. 19B illustrate different events are saved and linkedaccording to different user policy from FIG. 7 and FIG. 6;

FIG. 20 shows an example of cross linked contact record accessible fromthe calendar application;

FIG. 21 shows an example of uploading saved communication events to aremote computer or system.

FIG. 22 shows a flow diagram of a sample system encapsulating a computerprogram implementing the invention.

FIG. 23A is a functional block diagram of a system encapsulating acomputer program implementing the invention.

FIG. 23B is a functional block diagram of a system uploading a computerprogram implementing the invention for possible re-packaging andre-distribution.

FIG. 24 is a flow diagram of a system executing a downloaded orinstalled computer program which implements the invention from a storagemedium available to the communication terminal device.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

Hereinafter, certain embodiments of the present invention will bedescribed with reference to the accompanying drawings. In the drawings,only details necessary for understanding the invention are shown. Also,in the following description of the present invention, a detaileddescription of known functions and configurations which are evident foranyone skilled in the art will be omitted in order to emphasize thecharacteristics of the invention.

In a preferred embodiment of the present invention illustrated in FIG.1, a functional block diagram of the method is implemented on acommunication terminal device. A user establishes a telephonycommunication event on the first terminal device with one or pluralityof second terminal devices through a communication network. On the firstterminal device, there is a commonly available telephony module 101which retrieves the communication (or call) status, extracts the messagebody (or content) of the communication, and obtains the calleridentification (caller ID) of other calling parties if available. Thecommonly available telephony module can be a caller ID box or anApplication Programming Interface (API) for on-device software. Anotheron-device universal timer module 102 extracts the time of thecommunication event.

Information such as call status, caller ID's, and time stamp of thecommunication event are passed from the telephony and timer modules to atelephony extraction module 103 to invoke the event-driven informationcapturing and annotation process 104. Generic caller ID's and timestamps are converted to formats related to the target applications also103. In the preferred embodiment of the invention, converted caller ID'sare phone numbers for a phone book 109 and the time stamp is adjusted tothe local time zone for a calendar 110.

Separately, the user can select policy or settings which constitute atarget application with desired features available on the first terminaldevice 106. As shown in the preferred embodiment of the invention, suchapplication can be a customized organizer which integrates phone book109, calendar 110, and note pad 111 available on the first terminaldevice.

The user's selection of policy is assembled 105 and processed 104through a data extraction interface 107 which interacts with variousstand-alone applications. In the preferred embodiment of the invention,processed user policy is stored as custom application settings 108.

As the in-progress status of the communication event is detected 103,the information and policy process module 104 collects policy settings,related application data, caller ID's and time stamp related to thecommunication event. At the end of the communication event, the user isnotified and prompted with collected information and entries for furtherannotation or selection 112.

If user annotates the communication event with additional informationand saves related information 113 to the call event, data for variousapplications are saved through the data extraction interface 107 tostorage available to the first terminal device.

Stored event information with annotation can be retrieved 113 throughthe data extraction interface 107 to be further transmitted to othersystems or devices for specific purposes 114.

FIG. 2 shows a flow diagram of an embodiment of the invention where theterminal device integrates information from the communication network,user settings, and user policy available at the terminal device for.target application and prompts user for additional annotation to thecommunication event.

The communication event between the user at a first terminal device andthe other calling parties at secondary terminal devices is in one of thevoice, textual, video, or other formats. The type of the communicationevent is in one of the incoming or outgoing directions. Upon asuccessful connection of the communicating parties, information relatedto the event is sent to a system which implements a preferred embodimentof the invention 201 on a terminal device.

From the commonly available telephony and timer modules which interfacewith the communication network from the first terminal device, onlycaller ID's, event status, and network calibrated time stamp areextracted 202. Generic formats of the caller ID's, event status, andtime of the communication event are passed to various modules forfurther processing 203.

Related user settings and application data 204, which are available tothe terminal device are fetched for processing related informationextracted from the communication network.

In the preferred embodiment of the invention, caller ID's for anin-progress communication event is extracted in the format of phonenumber 205, for example, to be compared with the phone book directory toobtain a person's name if found 207. The time of the event is convertedto local time 206 according to user setting for a calendar event 204also.

Default or user's policy on targeted application 208 is obtained beforethe assembly of the user prompts for additional annotation or furtherselection 209. In the preferred embodiment of the invention, assembleduser prompts for annotation and selection are combined with an audioalert which notifies the user on the readiness of the user prompts 210.

As shown in FIG. 3, the telephony module on a terminal device 302extracts information including caller ID's and the status of thecommunication event 301 from the telecommunication network. Genericformat of the caller ID's, textual message, and status notification 303are made available to the extraction module, 103 of FIG. 1, from thecommon telephony module. The telephony information extraction module,103 of FIG. 1, reads the generic telephony information 303, and checksthe status of the communication event 304. If the communication is notestablished, there is no event-driven information annotation to thecommunication event 307. In the preferred embodiment of the invention,there is no call logger page for unsuccessful communication. In case thecommunication established successfully, one or plural caller ID's ofother participating parties are converted 305 into preferred format suchas phone numbers or Internet Protocol (IP) addresses 306 and passed tothe information and policy processing module, 104 of FIG. 1.

If there are related user settings and application data such as timezone and phone book available on the terminal device, FIG. 4 shows morespecific information such as caller name and time zone can be extracted.The intermediate format of caller ID's 401 are compared 403 with acontact directory such as phone book 402 on the terminal device. Ifnames are found with the intermediate format of caller ID's 401, theuser settings (e.g., time zone) and caller names 405 are passed to theinformation and policy processing module, 104 of FIG. 1. Otherwise, theintermediate caller ID's are packaged with user settings 404 for eventannotation.

In an example illustrated in FIG. 11, the user can set local time zone1101 from the terminal device under the options module 1102. The timezone setting is saved as on device data for applications such ascalendar.

In an embodiment of the invention illustrated in FIG. 5, there arepre-installed policy templates offered by applications available on theterminal device 501 and pre-defined program library configurable by theuser 504. User is prompted on selecting or setting policy and featuresfrom the template library 502. For example, if the terminal device isequipped with calendar, phone book, and message sender, one of the usertemplates can include adding follow up events 121 while saving the callevent and forwarding annotated communication events to a specificcontact 122 for an elite caller 123 as shown in FIG. 12.

In FIG. 5, when the user selects policy settings 503, some of theprogram modules 504 are enables or disabled. Optional data attributesmay be used to identify, for example, the elite clients. Afterprocessing the user preference on the policy 505, such settings may bestored 506 on a storage medium 108 available to the terminal device forthe information and policy processing module 104 in FIG. 1.

FIG. 13 demonstrates a result from a user defined policy in FIG. 12. Theoriginal call event 131 is saved along with a message to a contact 132and a new task scheduled as a follow up to this call 133.

An embodiment of the invention on processing the pre-set or stored userpolicy is illustrated in FIG. 6. The user policy can be determinedexplicitly by the stored user's preference or implicitly by theexistence of data attributes for related applications 601. The extractedand processed caller ID's from an in-progress communication event isevaluated under the user policy for generating prompts to the user forefficient annotation 602. In the preferred embodiment of the invention,a caller ID in the format of a phone number is compared with a phonedirectory 603. If a name is found from the directory and the record hassufficient information such as unique index for linking to items in thecalendar, the saved call event will be linked to records in the phonedirectory 606 if the user's policy setting 604 is to cross link recordsamong application modules. Otherwise, the call event is saved as standalone calendar entry 612.

An example of policy driven user prompts is shown in FIG. 14B. At theend of the communication event, a call logger page is displayed alongwith alert sound. The call logger page reports type of the call asoutgoing 1411, time of the call adjusted to local time zone 1412, callerID 1415 and corresponding name found in the phone directory 1416. Thereare entry boxes for user to annotate more information to the event 1417and command links to save 1413 or discard 1414 the call event. The saveand link contact to a call event is implemented as a system policy onceuser selects to save the call event 1413.

Following the example in FIG. 14B, the user annotates more information1512 to the call logger page in FIG. 15B and saves the event to acalendar 1511. FIG. 16B shows the call event with annotation is saved tocorresponding local date and time 1611 in the calendar application 1612.The cross linked call event for a more complex user policy in FIG. 13can be verified in FIG. 18B from the contact record 1811 page withpointers to linked events 1812. FIG. 19B demonstrates the cross-linkedcall event 1911, a message to related contact 1912, and a follow upreminder 1913.

In FIG. 6, if the caller ID cannot be found in the phone directory andthe data attributes are not available, the application preparesdifferent prompts for user to collect basic information separately 605.Additional user preference is checked 607, if available, on saving theuser annotation to various application data. User can designate specificmodules like the phone directory only for saving the user annotationrelated to the call event 608 (e.g., save a new name with a new callerID only). In the preferred embodiment of the invention, all userannotations are saved along with the call event into related applicationdata 609. User preference on whether to link the saved application data,if available, is examined 610 before saving the annotation to separateapplication formats with all possible cross linking 611 among recordsrelated to the call event, or no cross link 612.

Another embodiment of the invention is illustrated in FIG. 7 where theuser policy setting process is interactive. In this case, the targetapplication such as organizer checks 703 the extracted and processedcaller ID's 702 (e.g., phone number) with application data 701 (e.g.,names and unique record index) for cross application linking (e.g.,links to calendar). If the caller name and application data attributesare found for a given caller ID, the user is prompted 704 to link savedcall event with the contact 706 or just save the annotated event toseparate application formats 710.

In FIG. 7, if the caller ID cannot be found in the phone directory, theapplication prepares various prompts 705 for user to save annotation toselected application modules only 707 or save annotation with cross linkamong application data 708. In the preferred embodiment of theinvention, the user can answer the prompt 707 to save annotation for aselected application 709 or for all related applications separately 710.Alternatively, the user can answer the prompt 708 to link saved userannotations among related applications 711 or no cross link among savedapplication data 710.

An example of the interactive user policy setting is show in FIG. 14A.At the end of the communication event, a call logger page is displayedalong with alert sound. The call logger page reports type of the call asoutgoing 1401, time of the call adjusted to local time zone 1402, callerID 1407 and temporary name for the phone directory 1408. There are entryboxes for user to annotate more information to the event 1409 andcommand links to save the new number only 1403, save the annotated callevent only 1404, save both new contact and link with annotate call event1406, or discard 1405 the call event.

Following the example in FIG. 14A, the user annotates more information1502, 1503, 1504, 1505 to the call logger page in FIG. 15A and saveswith cross links between both the new contact and the call event 1501.FIG. 16A shows the call event with annotation is saved to correspondinglocal date and time 1601 in the calendar application 1602. As shown inFIG. 17, user can perform record search 171 both in the contactdirectory 172 and event calendar 173 with the find application 174 toverify the saved new contact and call event. The search returns both thecall event 175 and the new contact 176 found on the storage available onthe terminal device.

The cross linked call event can be verified in FIG. 18A from the contactrecord page 1801, 1805 with newly added phone number 1802, assignedcontact name 1803, and pointers to linked events 1804. FIG. 19Ademonstrates the cross-linked call event 1901 in the calendarapplication 1902.

An embodiment of the invention on cross linking data from variousapplication modules is illustrated in FIG. 8. The user or policy settingdemands a creation of an item in application 2 with reference to arecord in application 1801 on a system available at the terminal device.The system fetches the object index from application 1802 as a data flagfor application 2 and assembles with input information 801 forapplication 2 803. The new item for application 2 is saved withreference to the object index or pointer to the record in application 1804. After the new item is saved for application 2, the system preparesuser prompts 805 with summary of the item in application 2 and a link orpointer to the related record in application 1 806 for confirmation.

An example of cross linked event is shown in FIG. 20. The user createsan event FIG. 20(2) from a record in the contact directory in FIG.20(1). The system saves the new event with cross link to the contact 20land displays a summary page with a link to phone numbers or emailaddresses of the contact as shown in. FIG. 20(3). When user selects thelink to the contact, the contact's phone number and email address aredisplayed for easy access as shown in FIG. 20(4).

In the preferred embodiment of the invention, a data flow diagram ofsaving the annotated communication event following the default or userpolicy is illustrated in FIG. 9. The assembled user annotation 901 tothe communication event is checked on whether the policy demands savingto storage device for various application modules 902. If the annotatedcommunication event is not saved, the system will go to designated endpoint 903 such as returning to screen display before the call. If thepolicy dictates saving the annotated communication event, a postprocessing is performed 904 to generate individual data for variousapplications 905, 906, 907.

An example on utilizing the saved communication events with annotationis illustrated in FIG. 10. Saved application data 1002, 1003, and 1004can be extracted and reformatted 1005 following the policy 1001 fortransmitting to other application or system 1006. Other application orsystem can also deposit application data 1002, 1003, 1004 and updatesthe user policy 1001 through the data extraction module 1005 on theterminal device. FIG. 21 shows a data upload policy is executed on savedcommunication events 211 to a remote computer system. A report page isdisplayed on the status of the transmission 212.

An example of a computer system encapsulating the preferred embodimentof the invention is illustrated in FIG. 22. The system detects acommunication event 2201 and extracts the status, caller ID's, and timeof the communication event 2202. Extracted call status, caller ID's, andtimestamp of the communication event 2203 are fed into a computerprogram implementing the invention 2207 with details shown in FIG. 1.Application data and settings from the user 2204 along with userannotation to the communication event 2205 (e.g., add notes and flagprogress of related project) are available to the computer program 2207also. The computer program implementing the preferred embodiment of theinvention 2207 is configured by the user or system defined policy 2206which determines templates and programs for features of the targetapplications and prompts for collecting the user annotation 2204.Processed information is saved into various formats for differentapplications in the system 2208, 2209, and 2210. A consecutive processcan be invoked to perform further tasks on the saved and linked, ifrequired, data according to the objective of the system 2211.

The computer program implementing the invention 2302 can be downloadedto a storage medium by a user as shown in FIG. 23A. The storage mediumcan be a removable card 2303, for example, or a persistent storagedevice 2304 available to the user at the first communication terminaldevice. The computer program can be invoked automatically (or “woke up”)by an in-progress communication event 2301 to capture relatedinformation from the user, application data, and the communication eventfor further processing at a higher system level as shown in FIG. 22.

A content or application service center can upload the computer programimplementing the invention 2311 to a server as shown in FIG. 23B. Theapplication server can package the computer program with relatedapplication and redistribute it to the storage of the terminal devicesfor an integrated communication event-driven service on the terminaldevices.

The asynchronous program download in FIG. 23A and communicationevent-driven information capturing in a system encapsulating theinvention is shown in FIG. 24. The user can download the computerprogram implementing the invention 2401 to a storage medium 2402 via thesame or different communication network where the communication eventtakes place. Or the user can install the computer program implementingthe invention 2401 to a storage medium 2402 from a removable mediareader device. When the communication event takes place 2403, thecommonly available telephony and timer modules on the communicationterminal extracts communication status, caller ID's, and event time2404. The “in-progress” call status and the availability of the computerprogram are checked 2406 to determine whether to proceed to theinformation annotation or to a system defined handling on acommunication event 2407 such as simply connect the call or route thecall to a voice mail if not answered.

If the communication establishes successfully and the computer programis ready for use, the system invokes the computer program implementingthe invention 2408. The program will fetch and process 2409 relatedinformation from the communication event 2405, user settings,application data 2410, policy for target applications 2411, and userannotation to the event 2412. Various application data are generated fornext level information processing 2413, 2414, and 2415.

Although the preferred embodiments of the present invention have beendisclosed for illustrative purposes, those skilled in the art willappreciate that various modifications, additions and substitutions arepossible, without departing from the scope and spirit of the inventionas disclosed in the accompanying claims.

1. A method for capturing at a first electronic device informationconcerning a telephony communication event occurring in telephoniccommunication between said first device and a second electronic device,said method comprising: receiving at the first device information thatidentifies a telephone number or Internet Protocol address with isassociated with said second electronic device, and through which saidsecond electronic device is in telephonic communication with the firstelectronic device; checking in a directory in a storage available at thefirst device, a person's name associated with said telephone number orInternet Protocol address; and storing at the first device informationconcerning the person's name associated with said telephone number orInternet Protocol address, if found, or the information that identifiesthe telephone number or Internet Protocol address, and informationregarding the telephony communication event.
 2. The method of claim 1,wherein in said storing, the first device automatically stores in acalendar in a storage available at the first device, informationconcerning the person's name associated with said telephone number orInternet Protocol address, if found, or the information that identifiesthe telephone number or Internet Protocol address.
 3. The method ofclaim 1, wherein the first device does not automatically erase thestored information when the first device subsequently stores informationconcerning a person's name associated with a new telephone number orInternet Protocol, address, or information identifying a new telephonenumber or Internet Protocol address.
 4. The method of claim 1, furthercomprising linking associating the telephony communication event withinformation concerning the person's name associated with said telephonenumber or Internet Protocol address, if found, or the information thatidentifies the telephone number or Internet Protocol address.
 5. Themethod of claim 4, wherein in said storing, pointers are stored thatlink the telephony communication event with information concerning theperson's name associated with said telephone number or Internet Protocoladdress, if found, or the information that identifies the telephonenumber or Internet Protocol address.
 6. A computer readable storagedevice embodying a program of instructions executable by a computer toperform a method of capturing at a first electronic device informationconcerning a telephony communication event occurring in telephoniccommunication between said first device and a second electronic device,said method comprising: receiving at the first device information thatidentifies a telephone number or Internet Protocol address which isassociated with said second electronic device, and through which saidsecond electronic device is in telephonic communication with the firstelectronic device; receiving at the first device information thatidentifies the time of said telephony communication event; checking in adirectory in a storage available at the first device, a person's nameassociated with said telephone number or Internet Protocol address; andstoring at the first device information concerning the person's nameassociated with said telephone number or Internet Protocol address, iffound, or the information that identifies the telephone number orInternet Protocol address, and information regarding the telephonycommunication event.
 7. The device of claim 6, wherein in said storing,the first device automatically stores in a calendar in a storageavailable at the first device, information concerning the person's nameassociated with said telephone number or Internet Protocol address, iffound, or the information that identifies the telephone number orInternet Protocol address.
 8. The device of claim 6, wherein the programdoes not automatically cause the first device to erase the storedinformation when the first device subsequently stores informationconcerning a person's name associated with a new telephone number orInternet Protocol address, or information identifying a new telephonenumber or Internet Protocol address.
 9. The device of claim 6, saidmethod further comprising linking the telephony communication event withinformation concerning the person's name associated with said telephonenumber or Internet Protocol address, if found, or the information thatidentifies the telephone number or Internet Protocol address.
 10. Thedevice of claim 9, wherein in said storing, pointers are stores thatlink the telephony communication event with information concerning theperson's name associated with said telephone number or Internet Protocoladdress, if found, or the information that identifies the telephonenumber or Internet Protocol address.